This repository was archived by the owner on Sep 8, 2025. It is now read-only.
Feature/edit succesfull voting on budgeting widget #383
Conversation
This file contains hidden or 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
Contributor
rudivanhierden
left a comment
rudivanhierden
left a comment
There was a problem hiding this comment.
succesfull is de verkeerde spelling, maar ik zie dat het voor step_3_succesfull_auth ook al zo stond. Zou wat mij betreft mooi zijn om dat voor beiden te corrigeren naar successful, wat vindt jij?
Verder inhoudelijk prima!
Contributor
Author
Heb voor de netheid de spelling aangepast voor de voting_title en een nieuwe PR geopend met de spelling correctie van successful_auth: https://github.com/openstad/openstad-frontend/pull/384/files |
LorenzoJokhan
deleted the
feature/edit-succesfull-voting-on-budgeting-widget
branch
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Description
Please include
Issue reference
Fixes # (issue)
Type of change
Is it a new feature, bug fix, code improvement, etc.
If it is a breaking change what needs to be done to fix that
Documentation
Is the documentation updated, maybe a link
Tests
(How) has the change been tested
Branch
If the branch to merge to is not development