-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename remaining article to thread #1138
Open
melroy89
wants to merge
12
commits into
dev/new_features
Choose a base branch
from
rename_article_to_thread
base: dev/new_features
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
melroy89
added
enhancement
New feature or request
frontend
Visual issues, improvements, bugs or other aspects relating mostly to the front end
backend
Backend related issues and pull requests
translation
Translation related pull request or issue
labels
Sep 19, 2024
BentiGorlich
requested changes
Sep 20, 2024
Ok I will look at it closer tomorrow. Code wise it looks good now |
This pr is less urgent than the 1.7.x fixes. No worries here. It's not really a bug fix. |
BentiGorlich
force-pushed
the
dev/new_features
branch
from
October 9, 2024 15:14
d07c5c3
to
fa6f302
Compare
Co-authored-by: Melroy van den Berg <melroy@melroy.org>
BentiGorlich
force-pushed
the
dev/new_features
branch
from
October 10, 2024 15:14
fa6f302
to
09a90b4
Compare
Rebased |
BentiGorlich
force-pushed
the
dev/new_features
branch
from
November 19, 2024 22:22
cf72318
to
7cd555b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
backend
Backend related issues and pull requests
enhancement
New feature or request
frontend
Visual issues, improvements, bugs or other aspects relating mostly to the front end
translation
Translation related pull request or issue
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rename all the remaining keywords from
article(s)
tothread(s)
. Making the code more consistent.Which also means I renamed the new valid link for creating a new thread:
new/thread
in the URL (same for the API).This PR also finally solves the translation strings that then where still have the key
article
,articles
,edit_article
(which was always missing btw),add_new_article
, etc. To the new keys:type.thread
,thread
,threads
,add_new_thread
and finallyedit_thread
.To be backwards compatible with existing data in the database (specifically the
type
column in theentry
table), we keep thearticle
string in theresolveType()
function, so t he old string "article" or "articles" are still valid. Same for some Twig templates, we extend with anotheror
for backwards compatibly for now.The next logical follow-up would be to rename
entry
as well later.