Skip to content

Conversation

@juliusknorr
Copy link
Member

Steps to reproduce the issue:

  • Create a new directory and open it
  • Manually create a README.md file and add some text to it
  • Click on the rich workspace placeholder to create a new file

Before:

  • A second file was created

After:

  • The rich workspace area will show the content of the existing file

As bonus this makes sure that when using external storages with a case-insensitive file system there will not be two separate files with different casing.

…pace

Signed-off-by: Julius Härtl <jus@bitgrid.net>
@juliusknorr juliusknorr added bug Something isn't working 3. to review labels Jun 26, 2020
@juliusknorr juliusknorr requested review from danxuliu and rullzer June 26, 2020 07:17
@juliusknorr juliusknorr added this to the 20.0.0 milestone Jun 26, 2020
@MorrisJobke MorrisJobke modified the milestones: 20.0.0, Nextcloud 20 Jul 7, 2020
@juliusknorr
Copy link
Member Author

/compile /

Signed-off-by: npmbuildbot[bot] <npmbuildbot[bot]@users.noreply.github.com>
Copy link
Member

@rullzer rullzer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks sane!

@juliusknorr juliusknorr merged commit 1da0582 into master Jul 9, 2020
@juliusknorr juliusknorr deleted the bugfix/noid/rich-workspace-check-before-creating branch July 9, 2020 07:46
@juliusknorr
Copy link
Member Author

/backport 4b3c40b to stable19

@juliusknorr
Copy link
Member Author

/backport 4b3c40b to stable18

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3. to review bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants