Frontmatter
| id | 4037 |
| title | util.HashHistory: push() => ignore duplicate entries |
| state | Closed |
| labels | enhancement |
| assignees | tobiu |
| createdAt | Feb 12, 2023, 9:26 PM |
| updatedAt | Feb 12, 2023, 9:26 PM |
| githubUrl | https://github.com/neomjs/neo/issues/4037 |
| author | tobiu |
| commentsCount | 0 |
| parentIssue | null |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| blockedBy | [] |
| blocking | [] |
| closedAt | Feb 12, 2023, 9:26 PM |
while the browser-based hashchange event won't trigger for changes to the same value, other internal logic could do this.
one such example is
controller.Application:me.importApp(path).then(module => { module.onStart(); // short delay to ensure Component Controllers are ready config.hash && setTimeout(() => HashHistory.push(config.hash), 5); });