Skip to content

Conversation

@ReenigneArcher
Copy link
Member

Description

When an application is saved, the current timestamp in milliseconds is added to as the application id. A timestamp was used instead of a random integer to prevent any chance of repeated values.

Screenshot

Issues Fixed or Closed

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Dependency update (updates to dependencies)
  • Documentation update (changes to documentation)
  • Repository update (changes to repository files, e.g. .github/...)

Checklist

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

Branch Updates

LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.

  • I want maintainers to keep my branch updated

@ReenigneArcher ReenigneArcher force-pushed the add/update-id-on-application-edit branch 3 times, most recently from 54b5462 to 7ebe092 Compare December 31, 2022 03:19
When an application is saved, the current timestamp in milliseconds is added to as the application id. A timestamp was used instead of a random integer to prevent any chance of repeated values.
@ReenigneArcher ReenigneArcher force-pushed the add/update-id-on-application-edit branch from 7ebe092 to 21660ea Compare December 31, 2022 14:50
@brad-richardson brad-richardson mentioned this pull request Jan 2, 2023
11 tasks
@ReenigneArcher
Copy link
Member Author

Closing in favor of #670

@ReenigneArcher ReenigneArcher deleted the add/update-id-on-application-edit branch March 8, 2023 14:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants