mirror of
https://github.com/actualbudget/actual.git
synced 2026-03-11 12:43:09 -05:00
d9a1260c91
* Update typography rule to disallow curly quotes with auto-fix - Reverse typography rule to detect and flag curly quotes instead of straight quotes - Add auto-fixer that converts curly quotes to straight quotes - Fix auto-fixer to properly escape quotes when they match string delimiters * Fix quotation marks in error messages and formatting strings across multiple files - Standardize quotation marks from curly to straight in error messages and string formatting for consistency. - Update various components and utility files to ensure proper string handling and improve readability. * Standardize quotation marks across multiple files - Replace curly quotes with straight quotes in various documentation and code files for consistency and improved readability. - Update error messages, comments, and documentation to ensure uniformity in string formatting. * Standardize month formatting across multiple components - Update month formatting strings from "MMMM 'yy" to "MMMM ''yy" in various components and utility files for consistency. - Ensure uniformity in how months are displayed throughout the application. * Refactor typography rule to enhance curly quote handling - Simplify the error reporting mechanism for curly quotes by creating a shared fix function. - Update test cases to include various curly quote scenarios for improved coverage. - Ensure consistent handling of curly quotes in formatting functions across multiple files. * Refactor typography handling and update tests for curly quotes - Replace curly quotes with their Unicode equivalents in typography rule and related test cases for consistency. - Remove unnecessary eslint-disable comments to improve code clarity. - Ensure proper handling of quotes in arithmetic and utility tests to align with updated typography standards. * Update VRT screenshots Auto-generated by VRT workflow PR: #6454 * Fix: Correct typo in budget cell notification message Co-authored-by: matiss <matiss@mja.lv> * Update VRT screenshots Auto-generated by VRT workflow PR: #6454 * Temporarily disable i18n string extraction workflow --------- Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: Cursor Agent <cursoragent@cursor.com>
46 lines
2.1 KiB
YAML
46 lines
2.1 KiB
YAML
name: Feature request
|
|
description: Request a missing feature
|
|
title: '[Feature] '
|
|
labels: ['feature']
|
|
type: Feature
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
Thanks for taking the time to fill out this feature request! Please ensure you provide as much information as possible so we can better understand what you're proposing so we can come up with the best solution for everyone.
|
|
- type: checkboxes
|
|
id: existing-issue
|
|
attributes:
|
|
label: 'Verified feature request does not already exist?'
|
|
description: "Please search to see if an issue or PR already exists for the feature you're requesting."
|
|
options:
|
|
- label: 'I have searched and found no existing issue'
|
|
required: true
|
|
- type: checkboxes
|
|
attributes:
|
|
label: '💻'
|
|
description: (Optional) Please check this box if you're willing to open a PR to implement this feature. We'll help you get started and answer any questions you have along the way :)
|
|
options:
|
|
- label: Would you like to implement this feature?
|
|
- type: textarea
|
|
id: pitch
|
|
attributes:
|
|
label: 'Pitch: what problem are you trying to solve?'
|
|
description: Please describe, in as much detail as you can, the problem that motivated you to submit this feature request.
|
|
validations:
|
|
required: true
|
|
- type: textarea
|
|
id: solution
|
|
attributes:
|
|
label: Describe your ideal solution to this problem
|
|
description: Feel free to give multiple different ideas for how the problem could be solved — we'd love to have a discussion to find the best way to solve your problem and related problems others may face! (Or leave this blank if you don't have a solution in mind yet.)
|
|
validations:
|
|
required: false
|
|
- type: textarea
|
|
id: learning
|
|
attributes:
|
|
label: Teaching and learning
|
|
description: How can we make sure future users find and enjoy this feature? (i.e. how do we make it discoverable? what kind of documentation should we write? are there aspects of the feature that could trip up users?)
|
|
validations:
|
|
required: false
|